Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1381

reference: 134-tree-1
name: 1381
tree-preservation-order: undefined
134-tpo-1
uprn
address-text
point: POINT (-1.032322 50.865230)
geometry: MULTIPOLYGON (((-1.032251 50.865222,-1.032254 50.865236,-1.032264 50.865249,-1.032280 50.865259,-1.032299 50.865265,-1.032321 50.865268,-1.032343 50.865266,-1.032363 50.865259,-1.032379 50.865250,-1.032389 50.865237,-1.032393 50.865223,-1.032390 50.865209,-1.032380 50.865197,-1.032365 50.865187,-1.032345 50.865180,-1.032323 50.865178,-1.032301 50.865180,-1.032281 50.865186,-1.032265 50.865196,-1.032255 50.865208,-1.032251 50.865222)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL